Skip to content

fix: hatch caused release pipeline failure#2168

Merged
degenaro merged 2 commits intodevelopfrom
fix-pipeline
Mar 18, 2026
Merged

fix: hatch caused release pipeline failure#2168
degenaro merged 2 commits intodevelopfrom
fix-pipeline

Conversation

@degenaro
Copy link
Collaborator

Types of changes

  • Hot fix (emergency fix and release)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Documentation (change which affects the documentation site)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Release (develop -> main)

Quality assurance (all should be covered).

  • My code follows the code style of this project.
  • Documentation for my change is up to date?
  • My PR meets testing requirements.
  • All new and existing tests passed.
  • All commits are signed-off.

Summary

Key links:

Before you merge

  • Ensure it is a 'squash commit' if not a release.
  • Ensure CI is currently passing
  • Check sonar. If you are working for a fork a maintainer will reach out, if required.

Signed-off-by: degenaro <lou.degenaro@gmail.com>
@degenaro degenaro requested a review from a team as a code owner March 18, 2026 11:43
Copy link
Member

@vikas-agarwal76 vikas-agarwal76 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@degenaro degenaro merged commit a430c69 into develop Mar 18, 2026
17 checks passed
@degenaro degenaro deleted the fix-pipeline branch March 18, 2026 11:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants